JST 'extractOutput' has been restored within the JST Task (2020.2.7)
Itential removed the extractOutput checkbox from the JST task in 2020.2.5, but after some consideration, decided to readd this configuration option back in 2020.2.7. Users now are able to change this value in Automation Studio.
Please note that between 2020.2.5 and 2020.2.7, this option defaulted to 'false.' Going forward, for new development, it will default to 'true' which will change the output when used with a single schema output JST as per the documentation. On the other hand, any existing development that had previously set this value to 'false' will be unchanged, but the user interface will allow the workflow designer to modify its value. Finally, any JST with an extractOutput=true that returns as undef, will cause the task to error and must be handled appropriately.
Indexing in the "job_history" collection (2020.2.7)
Prior to 2020.2.7, indexes were missing from the job_history collection, making certain operations time consuming and difficult. After applying the 2020.2.7 patch, please run the npm run index command in order to add the appropriate indexes for this collection. As a reminder, indexing operations vary depending on the size of your database so take caution when you choose to run it.
Modification to getJobDetails API (2020.2.7)
The GET /workflow_engine/job/:job_id/details API, or WorkFlowEngine.getJobDetails, has been modified as part of the 2020.2.7 maintenance release. Now, in addition to all the fields that existed before, the transitions field is also returned, which contains data from the workflow about how tasks connect to other tasks.
Adapter Deletion within Admin Essentials (2020.2.2)
Previously, Admin Essentals would not allow a user to delete an adapter that was in a profile. Now adapters can be deleted from Admin Essentials regardless of their status in the system profiles. On delete, a warning message will appear and then the adapter will be stopped and removed from every profile where it is found.
Problem Explanation
In an HA environment with three servers (i.e., IAP1, IAP2, IAP3), when an adapter instance is deleted from IAP1, two things happen:
- The adapter is "stopped" which kills the node process in IAP1.
- The adapter is removed from the profiles it is in.
Keep in mind that technically, IAP2 and IAP3 will still have their instance of the adapter running in memory. With the first action above, once the instance was deleted, the adapter was automatically "stopped" in IAP 1 only. This was not automatically applied for the other servers. Consequently, the user should also "stop" the adapter on IAP2 and IAP3. Otherwise, this could cause the instances in an HA environment to be out-of-sync.
New Job Details Permission
Viewing the Job Details pages now requires a new permission getJobDetails (defined within WorkflowEngine) that may not be enabled in some customers' custom roles. If you have custom roles and want those roles to access the Job Details page, then ensure they have access to either the WorkFlowEngine apiread role or the getJobDetails method. Hint: To do this, find the custom role in Authorization Manager, search for getJobDetails in the WorkFlowEngine application, and add it to the role.